Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d77e3cb61af86c839606e1ede46b17c3bd1a069f80358bb5234e082061717670

Tx prefix hash: f1bd99daad450d45df1ea0fc42073dfbd8f2cd1f0a04698fe3a845311a00a0b0
Tx public key: 332d107db22eba761fae3c158935fe0b2f4da4b28580da444d67d82e3388b6bc
Timestamp: 1745703745 Timestamp [UCT]: 2025-04-26 21:42:25 Age [y:d:h:m:s]: 00:204:13:17:50
Block: 1270143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143902 RingCT/type: yes/0
Extra: 01332d107db22eba761fae3c158935fe0b2f4da4b28580da444d67d82e3388b6bc021100000006f7011ad5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbea1fe24f9c9b373626e41815c4be0fd55060793b59e0522d4e8f8645b902b2 0.600000000000 1757384 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": 1270153, "vin": [ { "gen": { "height": 1270143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbea1fe24f9c9b373626e41815c4be0fd55060793b59e0522d4e8f8645b902b2" } } ], "extra": [ 1, 51, 45, 16, 125, 178, 46, 186, 118, 31, 174, 60, 21, 137, 53, 254, 11, 47, 77, 164, 178, 133, 128, 218, 68, 77, 103, 216, 46, 51, 136, 182, 188, 2, 17, 0, 0, 0, 6, 247, 1, 26, 213, 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