Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f144f95a9a79f943893647dceeb61abad340c9c07a58909cd7598e15a56451b

Tx prefix hash: 23e2912461f32c9a6bde174656a349951a431543f3bb8c4f97c6294c4d5f83f4
Tx public key: 9baefe24b8fa3e1591c4f87b8eddcc45d7d38f18a77db55b8d93a96221263d6b
Timestamp: 1720024496 Timestamp [UCT]: 2024-07-03 16:34:56 Age [y:d:h:m:s]: 00:273:16:25:55
Block: 1057762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195535 RingCT/type: yes/0
Extra: 019baefe24b8fa3e1591c4f87b8eddcc45d7d38f18a77db55b8d93a96221263d6b02110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35f185bee6ad20881cbefbde0650794d0b5dd49d607c1a5036a29396a7e05b8d 0.600000000000 1528203 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": 1057772, "vin": [ { "gen": { "height": 1057762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35f185bee6ad20881cbefbde0650794d0b5dd49d607c1a5036a29396a7e05b8d" } } ], "extra": [ 1, 155, 174, 254, 36, 184, 250, 62, 21, 145, 196, 248, 123, 142, 221, 204, 69, 215, 211, 143, 24, 167, 125, 181, 91, 141, 147, 169, 98, 33, 38, 61, 107, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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