Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e335e911b4a9df0aea564ac3c8c5d9487c78e572d2c4234a733840ce672587

Tx prefix hash: 6f00a60c28d971b0cfbcc0eb9e75fa110df930643f3938ce7077df7021f42eb4
Tx public key: 5ab4a3662b31563bee44562e9781483bb7cfdd4849c1839a1186d9ca12b6b0af
Timestamp: 1737773470 Timestamp [UCT]: 2025-01-25 02:51:10 Age [y:d:h:m:s]: 00:148:17:18:08
Block: 1204709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105940 RingCT/type: yes/0
Extra: 015ab4a3662b31563bee44562e9781483bb7cfdd4849c1839a1186d9ca12b6b0af021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7af35c0d9f8f81d526567227fe16f593606b473c29941d128e709f5f3e27938 0.600000000000 1691400 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": 1204719, "vin": [ { "gen": { "height": 1204709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7af35c0d9f8f81d526567227fe16f593606b473c29941d128e709f5f3e27938" } } ], "extra": [ 1, 90, 180, 163, 102, 43, 49, 86, 59, 238, 68, 86, 46, 151, 129, 72, 59, 183, 207, 221, 72, 73, 193, 131, 154, 17, 134, 217, 202, 18, 182, 176, 175, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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