Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0d846ee209ddd3a565e0ed84e66bf015632015b2afc204a940db5190363665

Tx prefix hash: 73ca70f1ab9e090643a5c0751b646f3839c03376e62fc2b27185498d00d06b43
Tx public key: e9f954a3df2823b0f40a30702646393750f97e00f68a1633c8df17c353a3acc7
Timestamp: 1743079030 Timestamp [UCT]: 2025-03-27 12:37:10 Age [y:d:h:m:s]: 00:239:02:23:45
Block: 1248398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168622 RingCT/type: yes/0
Extra: 01e9f954a3df2823b0f40a30702646393750f97e00f68a1633c8df17c353a3acc7021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39aec3fd9f106c87a4d4b6d269713f3f857e586f5cd4377a029c036994787f33 0.600000000000 1735427 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": 1248408, "vin": [ { "gen": { "height": 1248398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39aec3fd9f106c87a4d4b6d269713f3f857e586f5cd4377a029c036994787f33" } } ], "extra": [ 1, 233, 249, 84, 163, 223, 40, 35, 176, 244, 10, 48, 112, 38, 70, 57, 55, 80, 249, 126, 0, 246, 138, 22, 51, 200, 223, 23, 195, 83, 163, 172, 199, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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