Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ecd4eade0a0e607f75b1381ed0f120bfa77dd09e7b9f24c613f5dacd6041559

Tx prefix hash: e4bc5a8951c69e165194d8e98373515852fc7027d1bee40c245059ed5a9f743f
Tx public key: aa9184d944484c52d5b0dd9193bf4f22b2100e1563c354c6504a520af2942e4a
Timestamp: 1726593574 Timestamp [UCT]: 2024-09-17 17:19:34 Age [y:d:h:m:s]: 00:158:11:49:54
Block: 1112211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113064 RingCT/type: yes/0
Extra: 01aa9184d944484c52d5b0dd9193bf4f22b2100e1563c354c6504a520af2942e4a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8e54da09a328f381fb609dd4e072df5b2a87b383a190d66cd39a595e8320561 0.600000000000 1591454 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": 1112221, "vin": [ { "gen": { "height": 1112211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8e54da09a328f381fb609dd4e072df5b2a87b383a190d66cd39a595e8320561" } } ], "extra": [ 1, 170, 145, 132, 217, 68, 72, 76, 82, 213, 176, 221, 145, 147, 191, 79, 34, 178, 16, 14, 21, 99, 195, 84, 198, 80, 74, 82, 10, 242, 148, 46, 74, 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