Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 417aa95f05c1b6a150a57cb977de4ac860db6f5dfa5a465881df021c90ce85eb

Tx prefix hash: 6dd06988659ac7bd5b63a51f6e8b6ad835ce349125bf1ec296725479dbdf58cf
Tx public key: 47fc717a85ace4d89b3cbb2c027216670c3fe11e3e39d09271a523b389615e1a
Timestamp: 1724880826 Timestamp [UCT]: 2024-08-28 21:33:46 Age [y:d:h:m:s]: 00:216:19:40:13
Block: 1098009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154823 RingCT/type: yes/0
Extra: 0147fc717a85ace4d89b3cbb2c027216670c3fe11e3e39d09271a523b389615e1a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b50ce324d8184ebf05939a72a13a4c78989e644a0ca00d5f75a81f96274c10 0.600000000000 1573580 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": 1098019, "vin": [ { "gen": { "height": 1098009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b50ce324d8184ebf05939a72a13a4c78989e644a0ca00d5f75a81f96274c10" } } ], "extra": [ 1, 71, 252, 113, 122, 133, 172, 228, 216, 155, 60, 187, 44, 2, 114, 22, 103, 12, 63, 225, 30, 62, 57, 208, 146, 113, 165, 35, 179, 137, 97, 94, 26, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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