Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c6d9015debc4e97a0203676e4f953fb2b6c7f20d82f4f06f9307037845e7489

Tx prefix hash: 4aa9a1b49e940a1d27278a9a0ec65c14a3a1cf149240f0d978a841c800065c69
Tx public key: c05286e3f3420b4435da85499c95dd428ee21506254d8db500bbe10d9ecc436f
Timestamp: 1672683268 Timestamp [UCT]: 2023-01-02 18:14:28 Age [y:d:h:m:s]: 02:107:13:57:14
Block: 666143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598584 RingCT/type: yes/0
Extra: 01c05286e3f3420b4435da85499c95dd428ee21506254d8db500bbe10d9ecc436f02110000000733af99f4000000000000000000

1 output(s) for total of 3.808830751000 dcy

stealth address amount amount idx
00: e462929d836a5859d7e2d7e0333f8ace611b2c8430f99d26f4045011b3483ef2 3.808830751000 1107240 of 0

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": 666153, "vin": [ { "gen": { "height": 666143 } } ], "vout": [ { "amount": 3808830751, "target": { "key": "e462929d836a5859d7e2d7e0333f8ace611b2c8430f99d26f4045011b3483ef2" } } ], "extra": [ 1, 192, 82, 134, 227, 243, 66, 11, 68, 53, 218, 133, 73, 156, 149, 221, 66, 142, 226, 21, 6, 37, 77, 141, 181, 0, 187, 225, 13, 158, 204, 67, 111, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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