Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ce70233a9144a35d012c6f90669980b2520321590d49b116e76d062baa5e6a

Tx prefix hash: 7640928337dea716f4e804d620a76d04124fa2958fa098abc482566a73c15ac4
Tx public key: ed366d0b7ab69ffe60268af1e89cac90ee882aa557a30d7b68c1dd8eba0b1a3e
Timestamp: 1703820378 Timestamp [UCT]: 2023-12-29 03:26:18 Age [y:d:h:m:s]: 01:110:21:25:07
Block: 923417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340362 RingCT/type: yes/0
Extra: 01ed366d0b7ab69ffe60268af1e89cac90ee882aa557a30d7b68c1dd8eba0b1a3e021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6609665da1a24c29b6a291f90402d010e66ce4c2d9eec4fed97164e50fb643f 0.600000000000 1381149 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": 923427, "vin": [ { "gen": { "height": 923417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6609665da1a24c29b6a291f90402d010e66ce4c2d9eec4fed97164e50fb643f" } } ], "extra": [ 1, 237, 54, 109, 11, 122, 182, 159, 254, 96, 38, 138, 241, 232, 156, 172, 144, 238, 136, 42, 165, 87, 163, 13, 123, 104, 193, 221, 142, 186, 11, 26, 62, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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