Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7249f5a28084d9fa584cad989d242ea6362cca23ad28f683c313b3a7e2dea78

Tx prefix hash: 00a4d54111d2729ab8a89d2efc912207ad997bb1abab3e5002008b144a54ae2e
Tx public key: 863a1e40d1db119edc262300da7572b7ef3b1f2b186df179e9d82f832fcd2c77
Timestamp: 1648884523 Timestamp [UCT]: 2022-04-02 07:28:43 Age [y:d:h:m:s]: 02:311:14:28:48
Block: 471478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742162 RingCT/type: yes/0
Extra: 01863a1e40d1db119edc262300da7572b7ef3b1f2b186df179e9d82f832fcd2c7702110000002106faf294000000000000000000

1 output(s) for total of 16.819482589000 dcy

stealth address amount amount idx
00: 56bbc5522697de3b8c1b23c0131cbd8d5c3300e69b627b5c8a7c62dcb1f86a2c 16.819482589000 890822 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": 471488, "vin": [ { "gen": { "height": 471478 } } ], "vout": [ { "amount": 16819482589, "target": { "key": "56bbc5522697de3b8c1b23c0131cbd8d5c3300e69b627b5c8a7c62dcb1f86a2c" } } ], "extra": [ 1, 134, 58, 30, 64, 209, 219, 17, 158, 220, 38, 35, 0, 218, 117, 114, 183, 239, 59, 31, 43, 24, 109, 241, 121, 233, 216, 47, 131, 47, 205, 44, 119, 2, 17, 0, 0, 0, 33, 6, 250, 242, 148, 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