Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d0bf3b1da3ace49312127766bd3296330727732fd5578319c3596b517606d63

Tx prefix hash: d94df68061f109d245d9cff8cd4d978595418f9513435d49a7b72af0bbeee7ff
Tx public key: 14188a8633d49f33ce2e4f3e6d42a0eecd3ccf82ad72ebd2c6e5cb1146f3545a
Timestamp: 1687419646 Timestamp [UCT]: 2023-06-22 07:40:46 Age [y:d:h:m:s]: 01:207:16:00:02
Block: 787696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409802 RingCT/type: yes/0
Extra: 0114188a8633d49f33ce2e4f3e6d42a0eecd3ccf82ad72ebd2c6e5cb1146f3545a0211000000024b8f5122000000000000000000

1 output(s) for total of 1.506733040000 dcy

stealth address amount amount idx
00: b78354b9b3dbac862dd299c599bed2cf59573bcf75b1db001b069b7698593750 1.506733040000 1237771 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": 787706, "vin": [ { "gen": { "height": 787696 } } ], "vout": [ { "amount": 1506733040, "target": { "key": "b78354b9b3dbac862dd299c599bed2cf59573bcf75b1db001b069b7698593750" } } ], "extra": [ 1, 20, 24, 138, 134, 51, 212, 159, 51, 206, 46, 79, 62, 109, 66, 160, 238, 205, 60, 207, 130, 173, 114, 235, 210, 198, 229, 203, 17, 70, 243, 84, 90, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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