Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f3010a7eb93c4e521a6e9ed3e7a85d42cb16290745da05d902b4cc8e28747f

Tx prefix hash: b1e90da13c850f3137a7ed48194c42f67472d33f6c0b5b9781c11f50f18b24f7
Tx public key: a47fdffd5e6149bb3391162adea65e74cb96b30d607f4edc9d189ab91528bbe1
Timestamp: 1685084997 Timestamp [UCT]: 2023-05-26 07:09:57 Age [y:d:h:m:s]: 01:318:09:03:01
Block: 768340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488759 RingCT/type: yes/0
Extra: 01a47fdffd5e6149bb3391162adea65e74cb96b30d607f4edc9d189ab91528bbe102110000000375e3f0e9000000000000000000

1 output(s) for total of 1.746588900000 dcy

stealth address amount amount idx
00: 38ea4f0edafe3ab138b17d38d3c8f54564d55ff8b2d838f260fee6797d68e02f 1.746588900000 1217533 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": 768350, "vin": [ { "gen": { "height": 768340 } } ], "vout": [ { "amount": 1746588900, "target": { "key": "38ea4f0edafe3ab138b17d38d3c8f54564d55ff8b2d838f260fee6797d68e02f" } } ], "extra": [ 1, 164, 127, 223, 253, 94, 97, 73, 187, 51, 145, 22, 42, 222, 166, 94, 116, 203, 150, 179, 13, 96, 127, 78, 220, 157, 24, 154, 185, 21, 40, 187, 225, 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