Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b54c4b72db7cff4b75b8709c9e4845a0096fb4b562073ac60c516d288ae913e1

Tx prefix hash: 89b9310ff3e2d65e8efa40d207992a569a1a5fae8a26a4320956a1b774c72798
Tx public key: 6285a817a2f8153ebec7ef169e79154cf256bf3049b02e8c8f6379dbed800d79
Timestamp: 1728211768 Timestamp [UCT]: 2024-10-06 10:49:28 Age [y:d:h:m:s]: 00:181:00:21:50
Block: 1125646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129155 RingCT/type: yes/0
Extra: 016285a817a2f8153ebec7ef169e79154cf256bf3049b02e8c8f6379dbed800d7902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d72348c2f76f913f6df5482e03d9f8f5d64d4b7f0c6e481764e10ea109ef435b 0.600000000000 1608397 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": 1125656, "vin": [ { "gen": { "height": 1125646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d72348c2f76f913f6df5482e03d9f8f5d64d4b7f0c6e481764e10ea109ef435b" } } ], "extra": [ 1, 98, 133, 168, 23, 162, 248, 21, 62, 190, 199, 239, 22, 158, 121, 21, 76, 242, 86, 191, 48, 73, 176, 46, 140, 143, 99, 121, 219, 237, 128, 13, 121, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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