Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 941e9dfd0f4e6cbc150ce65d363bf4fed94da284a41686a8da07751d003ebe82

Tx prefix hash: 8d08516e32c9ddf035cbde1628375376ded33f14aeccc9717a1b835b1850c440
Tx public key: 5651adaac9e9371358344c56e9964a66c6928193aecf05d4dffb1e2d0325d7bc
Timestamp: 1753841175 Timestamp [UCT]: 2025-07-30 02:06:15 Age [y:d:h:m:s]: 00:112:20:38:46
Block: 1336337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79491 RingCT/type: yes/0
Extra: 015651adaac9e9371358344c56e9964a66c6928193aecf05d4dffb1e2d0325d7bc02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c9284fb4b7a12e5ccbd4e4a3a2a968c956f35280f4d0b380bbc130ac6744c8d 0.600000000000 1824138 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": 1336347, "vin": [ { "gen": { "height": 1336337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c9284fb4b7a12e5ccbd4e4a3a2a968c956f35280f4d0b380bbc130ac6744c8d" } } ], "extra": [ 1, 86, 81, 173, 170, 201, 233, 55, 19, 88, 52, 76, 86, 233, 150, 74, 102, 198, 146, 129, 147, 174, 207, 5, 212, 223, 251, 30, 45, 3, 37, 215, 188, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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