Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d3b86f7de623059bb7e4fd1f4469107b0006f81fba29545abe2b5803695fa10

Tx prefix hash: 16a2c22b92107d643e9b7db6f99d51836531903568fe66c35aa587be0f25412c
Tx public key: 9dfeadd1a26da766c8ab08ef286540795afb96fa622a7e81f9e8aff58091e34f
Timestamp: 1757769878 Timestamp [UCT]: 2025-09-13 13:24:38 Age [y:d:h:m:s]: 00:057:03:09:19
Block: 1367575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40917 RingCT/type: yes/0
Extra: 019dfeadd1a26da766c8ab08ef286540795afb96fa622a7e81f9e8aff58091e34f021100000008b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b1d805a9c3a17f92c8d847e20630634076e126aae3a4980b8238b0be4c2c897 0.600000000000 1855614 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": 1367585, "vin": [ { "gen": { "height": 1367575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b1d805a9c3a17f92c8d847e20630634076e126aae3a4980b8238b0be4c2c897" } } ], "extra": [ 1, 157, 254, 173, 209, 162, 109, 167, 102, 200, 171, 8, 239, 40, 101, 64, 121, 90, 251, 150, 250, 98, 42, 126, 129, 249, 232, 175, 245, 128, 145, 227, 79, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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