Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8421476f255c3473b7638e6d549be04f108862b6a5fc5d8ed0083adb791d1186

Tx prefix hash: 76862c89f6df623f490e6bad3a99d2df22164f7a4f29b56d5f12bdbd8191430e
Tx public key: b7f68b6a9438dd69c603995d5ec5ea2fed05946c940ddafea8966715139ed04f
Timestamp: 1725604172 Timestamp [UCT]: 2024-09-06 06:29:32 Age [y:d:h:m:s]: 00:261:01:28:09
Block: 1104021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186466 RingCT/type: yes/0
Extra: 01b7f68b6a9438dd69c603995d5ec5ea2fed05946c940ddafea8966715139ed04f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1163a0062b4d3d330aa2bdc5c57995e5c5e9667ffea808cc3b72f00127e6dd7 0.600000000000 1581076 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": 1104031, "vin": [ { "gen": { "height": 1104021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1163a0062b4d3d330aa2bdc5c57995e5c5e9667ffea808cc3b72f00127e6dd7" } } ], "extra": [ 1, 183, 246, 139, 106, 148, 56, 221, 105, 198, 3, 153, 93, 94, 197, 234, 47, 237, 5, 148, 108, 148, 13, 218, 254, 168, 150, 103, 21, 19, 158, 208, 79, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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