Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 165153e1abb058d8a7136fb7616cc455831243b87cdb7f48132b26c981fb045c

Tx prefix hash: 80ae0814bfed43b1ed99eb2f9cbc28d45e9991ab0f6c62ef4979a256ee7548f2
Tx public key: f72ce3b4a071d7398a2812b155b672d7b0ff12ae70afc2b790f5b0a7a7757529
Timestamp: 1741281230 Timestamp [UCT]: 2025-03-06 17:13:50 Age [y:d:h:m:s]: 00:006:00:01:32
Block: 1233528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4302 RingCT/type: yes/0
Extra: 01f72ce3b4a071d7398a2812b155b672d7b0ff12ae70afc2b790f5b0a7a7757529021100000003007f978a000000000000000000

1 output(s) for total of 0.600050000000 dcy

stealth address amount amount idx
00: 39847899d69acd514ab8f70326257666e7d40dbc05d39c75e6380e53b1d0abcd 0.600050000000 1720449 of 0

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": 1233538, "vin": [ { "gen": { "height": 1233528 } } ], "vout": [ { "amount": 600050000, "target": { "key": "39847899d69acd514ab8f70326257666e7d40dbc05d39c75e6380e53b1d0abcd" } } ], "extra": [ 1, 247, 44, 227, 180, 160, 113, 215, 57, 138, 40, 18, 177, 85, 182, 114, 215, 176, 255, 18, 174, 112, 175, 194, 183, 144, 245, 176, 167, 167, 117, 117, 41, 2, 17, 0, 0, 0, 3, 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