Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa9c9e027b8eca1c15bf4e6fd1b7ba3bf47813e596e36da00d1e502ea2bfb86

Tx prefix hash: 350564fc3d419a03635989bd888c07666ebcd738fa2b6fb2ce7cd1ca6c0f55c5
Tx public key: 4779a6fc777a5c006bdca35480897efb6bb39e4bd6ec532f33b7dd9cb8cae205
Timestamp: 1745760157 Timestamp [UCT]: 2025-04-27 13:22:37 Age [y:d:h:m:s]: 00:053:14:48:56
Block: 1270609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38207 RingCT/type: yes/0
Extra: 014779a6fc777a5c006bdca35480897efb6bb39e4bd6ec532f33b7dd9cb8cae20502110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eadf0ac9f1f5b0414addd0c815044e4c460ae793a867132428a32d52fd6ec31a 0.600000000000 1757852 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": 1270619, "vin": [ { "gen": { "height": 1270609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eadf0ac9f1f5b0414addd0c815044e4c460ae793a867132428a32d52fd6ec31a" } } ], "extra": [ 1, 71, 121, 166, 252, 119, 122, 92, 0, 107, 220, 163, 84, 128, 137, 126, 251, 107, 179, 158, 75, 214, 236, 83, 47, 51, 183, 221, 156, 184, 202, 226, 5, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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