Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 014cf30cfea078c4d4e9b2860e3710c48fa09f45d9207aa698ec40707e7cdc10

Tx prefix hash: d8361ea0a961774c87d0f1293c21103b8b7c5d1012180f83035e29819c28d448
Tx public key: 994a445cadec91a4ed5d048dc6c9343cd11edee85bac17cb24e196c121845b0f
Timestamp: 1715124174 Timestamp [UCT]: 2024-05-07 23:22:54 Age [y:d:h:m:s]: 00:187:06:44:45
Block: 1017134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134057 RingCT/type: yes/0
Extra: 01994a445cadec91a4ed5d048dc6c9343cd11edee85bac17cb24e196c121845b0f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 476a0cb0107257faa76d8f6b95097a5ff2e71bf7529fda0f7452146c67f8b76e 0.600000000000 1480901 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": 1017144, "vin": [ { "gen": { "height": 1017134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "476a0cb0107257faa76d8f6b95097a5ff2e71bf7529fda0f7452146c67f8b76e" } } ], "extra": [ 1, 153, 74, 68, 92, 173, 236, 145, 164, 237, 93, 4, 141, 198, 201, 52, 60, 209, 30, 222, 232, 91, 172, 23, 203, 36, 225, 150, 193, 33, 132, 91, 15, 2, 17, 0, 0, 0, 4, 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