Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 744df3ae682485ede2a81f8648d0d40c3e6887d0d15d611bf19dbcef75c54bd4

Tx prefix hash: 6c7c72ee735dcd0c169fccffa173973d99257a90249cac3ff4742948e0719d98
Tx public key: 1873e7b46e66ca0e8561a1dac995af86057e6ebfdab807c5eaab2d4e61b94d89
Timestamp: 1716775346 Timestamp [UCT]: 2024-05-27 02:02:26 Age [y:d:h:m:s]: 00:350:17:33:32
Block: 1030828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250690 RingCT/type: yes/0
Extra: 011873e7b46e66ca0e8561a1dac995af86057e6ebfdab807c5eaab2d4e61b94d89021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 180f65c6fa91b029f1b16d62a6665a248bcb24d7b9fc8a92a36a85391a8343b4 0.600000000000 1499129 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": 1030838, "vin": [ { "gen": { "height": 1030828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "180f65c6fa91b029f1b16d62a6665a248bcb24d7b9fc8a92a36a85391a8343b4" } } ], "extra": [ 1, 24, 115, 231, 180, 110, 102, 202, 14, 133, 97, 161, 218, 201, 149, 175, 134, 5, 126, 110, 191, 218, 184, 7, 197, 234, 171, 45, 78, 97, 185, 77, 137, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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