Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9558c95ecf7ef38ef917c22aed7d22be92e8f4723f587dd32f5a4aec8b3e901

Tx prefix hash: fec0177dc5a16f3d2cef856fb636d4b05e301112288311f61f9cf63f4565d7e9
Tx public key: 73b6f623b19b9fd7b83783ff6e00854586fb50511768e1e99f27b7fc8cce17e3
Timestamp: 1721866389 Timestamp [UCT]: 2024-07-25 00:13:09 Age [y:d:h:m:s]: 00:263:07:57:58
Block: 1073027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188134 RingCT/type: yes/0
Extra: 0173b6f623b19b9fd7b83783ff6e00854586fb50511768e1e99f27b7fc8cce17e302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 778215653f11cc70454a79cc35c9d15f168dffd48ce3662fe8207fa210c25fd6 0.600000000000 1545526 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": 1073037, "vin": [ { "gen": { "height": 1073027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "778215653f11cc70454a79cc35c9d15f168dffd48ce3662fe8207fa210c25fd6" } } ], "extra": [ 1, 115, 182, 246, 35, 177, 155, 159, 215, 184, 55, 131, 255, 110, 0, 133, 69, 134, 251, 80, 81, 23, 104, 225, 233, 159, 39, 183, 252, 140, 206, 23, 227, 2, 17, 0, 0, 0, 4, 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