Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5a4aa759f92e6b3f8452b3877e9eaa893e28779ce9e8739c73e1617df04ab4

Tx prefix hash: 7a11773a0bb154e2579f709615b17238777c19093f96f5a3d75442fc1e5903aa
Tx public key: c1e4e065797adf51a9421f04a659ffd7889d889469fb576e35a7ff81c3847c6b
Timestamp: 1747226908 Timestamp [UCT]: 2025-05-14 12:48:28 Age [y:d:h:m:s]: 00:176:09:28:11
Block: 1282758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123747 RingCT/type: yes/0
Extra: 01c1e4e065797adf51a9421f04a659ffd7889d889469fb576e35a7ff81c3847c6b02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899d62b76b22fc140636bdd70c87f5841bb1e9f4e37ad07141931cd083b533eb 0.600000000000 1770169 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": 1282768, "vin": [ { "gen": { "height": 1282758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899d62b76b22fc140636bdd70c87f5841bb1e9f4e37ad07141931cd083b533eb" } } ], "extra": [ 1, 193, 228, 224, 101, 121, 122, 223, 81, 169, 66, 31, 4, 166, 89, 255, 215, 136, 157, 136, 148, 105, 251, 87, 110, 53, 167, 255, 129, 195, 132, 124, 107, 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