Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0471fa88198d62ade5c21ca4a5a40c71d96bc94d06bb77349b0cb3b30a3c56a

Tx prefix hash: 5ba65b3d2b355472c4893f5d4e1215192c5d240053346e37476ec208a4ec732d
Tx public key: 306c497135a6847cb22597d1ba03f1e1a1f274d3d9f19414ea97d1a66875ed25
Timestamp: 1760688523 Timestamp [UCT]: 2025-10-17 08:08:43 Age [y:d:h:m:s]: 00:020:14:07:56
Block: 1391771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14734 RingCT/type: yes/0
Extra: 01306c497135a6847cb22597d1ba03f1e1a1f274d3d9f19414ea97d1a66875ed250211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f871f439c0b56a4f3d370ff0a15b439e6c59e608ce7d60270fbb0eb3758da652 0.600000000000 1880018 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": 1391781, "vin": [ { "gen": { "height": 1391771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f871f439c0b56a4f3d370ff0a15b439e6c59e608ce7d60270fbb0eb3758da652" } } ], "extra": [ 1, 48, 108, 73, 113, 53, 166, 132, 124, 178, 37, 151, 209, 186, 3, 241, 225, 161, 242, 116, 211, 217, 241, 148, 20, 234, 151, 209, 166, 104, 117, 237, 37, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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