Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f2791d96d043de29fd2befe38d2074e5d9087cc436259b5f5a8da051045140

Tx prefix hash: 456a5a5dc5ad7db225f39b4720105372548ca680d5ab7a3079fa41c6e4f4b45c
Tx public key: 213ff60c915de767c60192d35153b9811cbbfef8d26c0729ae089f774824a9f2
Timestamp: 1705536173 Timestamp [UCT]: 2024-01-18 00:02:53 Age [y:d:h:m:s]: 01:307:05:22:31
Block: 937622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478410 RingCT/type: yes/0
Extra: 01213ff60c915de767c60192d35153b9811cbbfef8d26c0729ae089f774824a9f202110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c97e1d1339d1cd80a476cdab7a7278e1050affa21fee5edb3ce062ae6dd8f2 0.600000000000 1395684 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": 937632, "vin": [ { "gen": { "height": 937622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c97e1d1339d1cd80a476cdab7a7278e1050affa21fee5edb3ce062ae6dd8f2" } } ], "extra": [ 1, 33, 63, 246, 12, 145, 93, 231, 103, 198, 1, 146, 211, 81, 83, 185, 129, 28, 187, 254, 248, 210, 108, 7, 41, 174, 8, 159, 119, 72, 36, 169, 242, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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