Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44fc8db94bd277d6e1a70f646fd2e76c2b673d01ebde1aa5c4cbd617db51bd77

Tx prefix hash: 21e5fbc71563a9d6d931e94850ce1e32bf487353f8566e9abfc8b72e1bd2e902
Tx public key: 68c0e01baafbda63c1ec8cc4ed9e608fe0a020b92fb1b704947186c230b1217a
Timestamp: 1720857355 Timestamp [UCT]: 2024-07-13 07:55:55 Age [y:d:h:m:s]: 01:117:11:14:44
Block: 1064680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342452 RingCT/type: yes/0
Extra: 0168c0e01baafbda63c1ec8cc4ed9e608fe0a020b92fb1b704947186c230b1217a02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df791ea646157d18aa493a27982afe8e8180c186fb3966a2de777ff4bbab3877 0.600000000000 1535211 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": 1064690, "vin": [ { "gen": { "height": 1064680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df791ea646157d18aa493a27982afe8e8180c186fb3966a2de777ff4bbab3877" } } ], "extra": [ 1, 104, 192, 224, 27, 170, 251, 218, 99, 193, 236, 140, 196, 237, 158, 96, 143, 224, 160, 32, 185, 47, 177, 183, 4, 148, 113, 134, 194, 48, 177, 33, 122, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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