Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc6049cf4d50eec3df9cc80012e2e3330eae4dfd1c0946ca1fdac9c22feb94c

Tx prefix hash: 0e769a28467f1b9e292b051c4cb8b17d59fbb9e790842aefb72931572e47679c
Tx public key: 73d3b694dc202202f23474d7c2817d79d225b2c7278bf21e29c74682efe334a6
Timestamp: 1751540265 Timestamp [UCT]: 2025-07-03 10:57:45 Age [y:d:h:m:s]: 00:134:09:26:45
Block: 1317881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94304 RingCT/type: yes/0
Extra: 0173d3b694dc202202f23474d7c2817d79d225b2c7278bf21e29c74682efe334a602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba796699e335364d6e80c815070533a54b9408e62c1e3edfa628afa863382a0d 0.600000000000 1805552 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": 1317891, "vin": [ { "gen": { "height": 1317881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba796699e335364d6e80c815070533a54b9408e62c1e3edfa628afa863382a0d" } } ], "extra": [ 1, 115, 211, 182, 148, 220, 32, 34, 2, 242, 52, 116, 215, 194, 129, 125, 121, 210, 37, 178, 199, 39, 139, 242, 30, 41, 199, 70, 130, 239, 227, 52, 166, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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