Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 088a4219d693cfa45caf76fff0ad7822a5315a4a92088a4b717e9b71f4b35ea8

Tx prefix hash: 36975284d75547a1a8b8e423c3d9e559165a16a5cb7d46c099a64860eea7c38d
Tx public key: ea38e10042331bf298baa2140ceab8eff8c8ce7bd410220efb76e230056c64dd
Timestamp: 1693372606 Timestamp [UCT]: 2023-08-30 05:16:46 Age [y:d:h:m:s]: 01:078:07:27:40
Block: 836981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317268 RingCT/type: yes/0
Extra: 01ea38e10042331bf298baa2140ceab8eff8c8ce7bd410220efb76e230056c64dd02110000000875e3f0e9000000000000000000

1 output(s) for total of 1.034509720000 dcy

stealth address amount amount idx
00: 4372be0e89a023cc9202bdfc39a109e875149d8ed206c3737df41eecc32828c1 1.034509720000 1289589 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": 836991, "vin": [ { "gen": { "height": 836981 } } ], "vout": [ { "amount": 1034509720, "target": { "key": "4372be0e89a023cc9202bdfc39a109e875149d8ed206c3737df41eecc32828c1" } } ], "extra": [ 1, 234, 56, 225, 0, 66, 51, 27, 242, 152, 186, 162, 20, 12, 234, 184, 239, 248, 200, 206, 123, 212, 16, 34, 14, 251, 118, 226, 48, 5, 108, 100, 221, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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