Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f6e024ce8c09c4d06113db331f56b0cb1c416c16ae49a4dca022a95fddd571

Tx prefix hash: 8f6e39f13f312d03184bb426070cefbc5a785df67eab68a875af8faf1a3654f9
Tx public key: 4aef77d83e37a39b9531ac61ae9502804d29001f22403dbce3333b39b41ff809
Timestamp: 1750714849 Timestamp [UCT]: 2025-06-23 21:40:49 Age [y:d:h:m:s]: 00:148:16:27:44
Block: 1311377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104193 RingCT/type: yes/0
Extra: 014aef77d83e37a39b9531ac61ae9502804d29001f22403dbce3333b39b41ff809021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0785fa450b5d20cb18508f4e5cacc07cce5aa8da06a81a7bc94844b1c382821 0.600000000000 1799004 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": 1311387, "vin": [ { "gen": { "height": 1311377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0785fa450b5d20cb18508f4e5cacc07cce5aa8da06a81a7bc94844b1c382821" } } ], "extra": [ 1, 74, 239, 119, 216, 62, 55, 163, 155, 149, 49, 172, 97, 174, 149, 2, 128, 77, 41, 0, 31, 34, 64, 61, 188, 227, 51, 59, 57, 180, 31, 248, 9, 2, 17, 0, 0, 0, 2, 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