Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf85bccc592473ba312c0338ba6730de6eb2b3a2e5a8f7db2f8f419e254c764b

Tx prefix hash: 1f4efc321e5fd431e42cd09884bed983de95980ae115255ed3f7e052c3d6d4a3
Tx public key: c30108f4c6c8b8eb67aed25848aca4ed6f658b443e50ee87d508bc4db081ed48
Timestamp: 1750107902 Timestamp [UCT]: 2025-06-16 21:05:02 Age [y:d:h:m:s]: 00:158:02:26:02
Block: 1306494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110786 RingCT/type: yes/0
Extra: 01c30108f4c6c8b8eb67aed25848aca4ed6f658b443e50ee87d508bc4db081ed48021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6af7cbfbf413ff9396c8dfe692854cbc7fcfd1cdddbe42e7c833fbe049cd377 0.600000000000 1794101 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": 1306504, "vin": [ { "gen": { "height": 1306494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6af7cbfbf413ff9396c8dfe692854cbc7fcfd1cdddbe42e7c833fbe049cd377" } } ], "extra": [ 1, 195, 1, 8, 244, 198, 200, 184, 235, 103, 174, 210, 88, 72, 172, 164, 237, 111, 101, 139, 68, 62, 80, 238, 135, 213, 8, 188, 77, 176, 129, 237, 72, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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