Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc87d65e58206e013514b6bb4dd0972d69818e8ae9c9e39529901a1e4637ef55

Tx prefix hash: ca17e63e20cc96b5f3dc8640a672f28282de3a92fde8efdf49bf6fd468426e7a
Tx public key: 41d0a933ca0282228ef759a932dbb43205a396a3c15a60bdd3fa16f2e51e43eb
Timestamp: 1760408776 Timestamp [UCT]: 2025-10-14 02:26:16 Age [y:d:h:m:s]: 00:023:23:17:13
Block: 1389462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17140 RingCT/type: yes/0
Extra: 0141d0a933ca0282228ef759a932dbb43205a396a3c15a60bdd3fa16f2e51e43eb0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07b04d9b16dadf454b4c572165168e222a86a0d9bcdd46ebf1fb70b424a01a7f 0.600000000000 1877691 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": 1389472, "vin": [ { "gen": { "height": 1389462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07b04d9b16dadf454b4c572165168e222a86a0d9bcdd46ebf1fb70b424a01a7f" } } ], "extra": [ 1, 65, 208, 169, 51, 202, 2, 130, 34, 142, 247, 89, 169, 50, 219, 180, 50, 5, 163, 150, 163, 193, 90, 96, 189, 211, 250, 22, 242, 229, 30, 67, 235, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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