Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f32dde31ebe01992618cb78c72d81eed332b0f847bccd533d2e425b7cca9ee

Tx prefix hash: d8cf6ccb3802b63e4f0242f5a911c8271f03df9043354e424f97716ec9b936eb
Tx public key: 22d4036949034e3774f96ab8b5c8f5a3f3feba8164e5d458453c687694d685f2
Timestamp: 1723347989 Timestamp [UCT]: 2024-08-11 03:46:29 Age [y:d:h:m:s]: 01:087:15:24:24
Block: 1085305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321099 RingCT/type: yes/0
Extra: 0122d4036949034e3774f96ab8b5c8f5a3f3feba8164e5d458453c687694d685f2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1bcd731a9fcfa887a1e1478512162cdcbd5c4b01b4d7c2a9425749214bacd8d 0.600000000000 1559862 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": 1085315, "vin": [ { "gen": { "height": 1085305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1bcd731a9fcfa887a1e1478512162cdcbd5c4b01b4d7c2a9425749214bacd8d" } } ], "extra": [ 1, 34, 212, 3, 105, 73, 3, 78, 55, 116, 249, 106, 184, 181, 200, 245, 163, 243, 254, 186, 129, 100, 229, 212, 88, 69, 60, 104, 118, 148, 214, 133, 242, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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