Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b48b173698158175ce0cd20c37defb65862b96f00e3f1f8046caa4905427ebd

Tx prefix hash: da28cc6ad4139af6fe877521d14ac9c47b9b9c0c16cc39a5a5eabe7bca4c3c1e
Tx public key: 17ca3cfea03f84924f01b94e6d76e5a0671dd0876405bdcf3889eb7a85a14f80
Timestamp: 1736253249 Timestamp [UCT]: 2025-01-07 12:34:09 Age [y:d:h:m:s]: 00:086:13:23:34
Block: 1192164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61635 RingCT/type: yes/0
Extra: 0117ca3cfea03f84924f01b94e6d76e5a0671dd0876405bdcf3889eb7a85a14f800211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fd2ca1a752a520b3255b51c0cb2eae3cb04abbd0b2286e5f073fa45d9929c89 0.600000000000 1678713 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": 1192174, "vin": [ { "gen": { "height": 1192164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fd2ca1a752a520b3255b51c0cb2eae3cb04abbd0b2286e5f073fa45d9929c89" } } ], "extra": [ 1, 23, 202, 60, 254, 160, 63, 132, 146, 79, 1, 185, 78, 109, 118, 229, 160, 103, 29, 208, 135, 100, 5, 189, 207, 56, 137, 235, 122, 133, 161, 79, 128, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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