Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa7fb4951cb681652a5b8e0d4df552fbe57bec49572bba613cb19b9dd30c2b03

Tx prefix hash: 659b54d7f22f65dcf1e8b98e7140636a17c95fb1a5ca618519fa0bf872599b8e
Tx public key: eb1bcd4f271ee90afec094d45695f98133e4f39dcce6521e374cfe8b6448c22c
Timestamp: 1728409522 Timestamp [UCT]: 2024-10-08 17:45:22 Age [y:d:h:m:s]: 00:162:05:37:47
Block: 1127274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115757 RingCT/type: yes/0
Extra: 01eb1bcd4f271ee90afec094d45695f98133e4f39dcce6521e374cfe8b6448c22c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e388e8c5b235448c789a2971dd029da1794f7408d6adb06fcd4c4ed0062621f6 0.600000000000 1610075 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": 1127284, "vin": [ { "gen": { "height": 1127274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e388e8c5b235448c789a2971dd029da1794f7408d6adb06fcd4c4ed0062621f6" } } ], "extra": [ 1, 235, 27, 205, 79, 39, 30, 233, 10, 254, 192, 148, 212, 86, 149, 249, 129, 51, 228, 243, 157, 204, 230, 82, 30, 55, 76, 254, 139, 100, 72, 194, 44, 2, 17, 0, 0, 0, 3, 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