Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db3ead8bb7703bf865972c002a2e898a72cb7a1fccb0c699596add810cd556e

Tx prefix hash: 724854390a2bfcffd51e7b1897bae1cbdac00e830026d9722b816489891f0149
Tx public key: 2983bae677abc1c2f1a3a1d97f6fc435d3c1f38832fc8d006671925ec5959ff3
Timestamp: 1701587641 Timestamp [UCT]: 2023-12-03 07:14:01 Age [y:d:h:m:s]: 01:056:12:34:26
Block: 904896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301540 RingCT/type: yes/0
Extra: 012983bae677abc1c2f1a3a1d97f6fc435d3c1f38832fc8d006671925ec5959ff302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.616174736000 dcy

stealth address amount amount idx
00: d8b140c49c8997491a1504a4024e1f391c662d80c38fb23ff1966d0ad4bf3901 0.616174736000 1361681 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": 904906, "vin": [ { "gen": { "height": 904896 } } ], "vout": [ { "amount": 616174736, "target": { "key": "d8b140c49c8997491a1504a4024e1f391c662d80c38fb23ff1966d0ad4bf3901" } } ], "extra": [ 1, 41, 131, 186, 230, 119, 171, 193, 194, 241, 163, 161, 217, 127, 111, 196, 53, 211, 193, 243, 136, 50, 252, 141, 0, 102, 113, 146, 94, 197, 149, 159, 243, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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