Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 858a29fcd8a648e6038825699b0316663c865782b3a3f3023163e8a455cec4c1

Tx prefix hash: 4fec8b3e34fef977f87f8cdd7d526585fed9f9bc7411fa77436b288990d10956
Tx public key: ecfbb38b0131aa50d4792e7a086bf8a3fbbdfe928e833428b1f3db94f625b67d
Timestamp: 1731396548 Timestamp [UCT]: 2024-11-12 07:29:08 Age [y:d:h:m:s]: 00:139:14:47:39
Block: 1151943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99610 RingCT/type: yes/0
Extra: 01ecfbb38b0131aa50d4792e7a086bf8a3fbbdfe928e833428b1f3db94f625b67d021100000006007f978a000000000000000000

1 output(s) for total of 0.605900000000 dcy

stealth address amount amount idx
00: 6ed30cedd134cc5c85df22861737091786d9a0e100807da57e20f886363d989e 0.605900000000 1637528 of 0

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": 1151953, "vin": [ { "gen": { "height": 1151943 } } ], "vout": [ { "amount": 605900000, "target": { "key": "6ed30cedd134cc5c85df22861737091786d9a0e100807da57e20f886363d989e" } } ], "extra": [ 1, 236, 251, 179, 139, 1, 49, 170, 80, 212, 121, 46, 122, 8, 107, 248, 163, 251, 189, 254, 146, 142, 131, 52, 40, 177, 243, 219, 148, 246, 37, 182, 125, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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