Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32b7ef7e163f4b45a27003b00a41e64064eae9a2d864e420311f1e57bad7f43

Tx prefix hash: 28aa7d920d42205f7c45dc18eea63fc5015317eafd64ef02d6533825a11cb76a
Tx public key: 3642af5d4162001ba22a1a681d54b6e9c60d57692586d18d81bbe73f29047694
Timestamp: 1695002534 Timestamp [UCT]: 2023-09-18 02:02:14 Age [y:d:h:m:s]: 01:160:19:45:36
Block: 850501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375995 RingCT/type: yes/0
Extra: 013642af5d4162001ba22a1a681d54b6e9c60d57692586d18d81bbe73f2904769402110000000a4b8f5122000000000000000000

1 output(s) for total of 0.933119324000 dcy

stealth address amount amount idx
00: e74baec614e0bcdb1557c6032626bad6fbd61e05c2898c65f3a7b56995eae9f9 0.933119324000 1304223 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": 850511, "vin": [ { "gen": { "height": 850501 } } ], "vout": [ { "amount": 933119324, "target": { "key": "e74baec614e0bcdb1557c6032626bad6fbd61e05c2898c65f3a7b56995eae9f9" } } ], "extra": [ 1, 54, 66, 175, 93, 65, 98, 0, 27, 162, 42, 26, 104, 29, 84, 182, 233, 198, 13, 87, 105, 37, 134, 209, 141, 129, 187, 231, 63, 41, 4, 118, 148, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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