Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 505b5d4ede32406a32fa7cc55ea027064c8cdc2dfbab57114ee8184a75bd97bc

Tx prefix hash: 22e582e8d5ab62a1b7ed8f4f5c2396a10547e552474cb6245de3a643365f3682
Tx public key: 0228ba58e13f55d5e7d2e2de3246df1d7f47c362e4e876c15f7a6303408cefe6
Timestamp: 1768147440 Timestamp [UCT]: 2026-01-11 16:04:00 Age [y:d:h:m:s]: 00:016:00:32:39
Block: 1453597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 11275 RingCT/type: yes/0
Extra: 010228ba58e13f55d5e7d2e2de3246df1d7f47c362e4e876c15f7a6303408cefe60209000000098970985800

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0a0f72da9f65086d94f3baa80c6d60b40dbf0452592365fde50e235f641a749 0.600000000000 1942663 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": 1453607, "vin": [ { "gen": { "height": 1453597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a0f72da9f65086d94f3baa80c6d60b40dbf0452592365fde50e235f641a749" } } ], "extra": [ 1, 2, 40, 186, 88, 225, 63, 85, 213, 231, 210, 226, 222, 50, 70, 223, 29, 127, 71, 195, 98, 228, 232, 118, 193, 95, 122, 99, 3, 64, 140, 239, 230, 2, 9, 0, 0, 0, 9, 137, 112, 152, 88, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8