Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6028186230bf65c35c203c3e6cc44f669fd17242cbfe82064d47b9c2e53c3b2

Tx prefix hash: 63f7d1e742a69e8b3951166c85731598c5ce2867a18f0063f1aef2322485e981
Tx public key: 03d742ba1f4fb6e05bc79a21dcbd0bb3134700fa3dc60e11ca02e5d403c605b5
Timestamp: 1759618919 Timestamp [UCT]: 2025-10-04 23:01:59 Age [y:d:h:m:s]: 00:042:18:31:04
Block: 1382898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30627 RingCT/type: yes/0
Extra: 0103d742ba1f4fb6e05bc79a21dcbd0bb3134700fa3dc60e11ca02e5d403c605b5021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c4475cd005a41e180a56acf0b2a96852cf5decd808f5dd144229a0a2259d024 0.600000000000 1871043 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": 1382908, "vin": [ { "gen": { "height": 1382898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c4475cd005a41e180a56acf0b2a96852cf5decd808f5dd144229a0a2259d024" } } ], "extra": [ 1, 3, 215, 66, 186, 31, 79, 182, 224, 91, 199, 154, 33, 220, 189, 11, 179, 19, 71, 0, 250, 61, 198, 14, 17, 202, 2, 229, 212, 3, 198, 5, 181, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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