Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 95a3d94ba331e0e81b464e1fa60496fbfe562c95a3fbb0b6bc5d931df2b965d7

Tx prefix hash: dd54a57dcb23c8ea130b77cdc9153173a1ff548a35b234878b2186415a58f75e
Tx public key: da321b40f67459d61fd7d493aa6cfd31a503170ac661556dc591436f2527fede
Timestamp: 1741187007 Timestamp [UCT]: 2025-03-05 15:03:27 Age [y:d:h:m:s]: 00:260:22:49:43
Block: 1232755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184233 RingCT/type: yes/0
Extra: 01da321b40f67459d61fd7d493aa6cfd31a503170ac661556dc591436f2527fede0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c5165c5cd2b6a7963d6697a073970b0d546588a0fcf9c28d41a16dd7f2f1d3e 0.600000000000 1719668 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1232765, "vin": [ { "gen": { "height": 1232755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c5165c5cd2b6a7963d6697a073970b0d546588a0fcf9c28d41a16dd7f2f1d3e" } } ], "extra": [ 1, 218, 50, 27, 64, 246, 116, 89, 214, 31, 215, 212, 147, 170, 108, 253, 49, 165, 3, 23, 10, 198, 97, 85, 109, 197, 145, 67, 111, 37, 39, 254, 222, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8