Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba21eb3ed46fa3c00eeb4aa470d02956b9827d10aed2e20d1e36987acfc45e80

Tx prefix hash: 5571445bfc7cb18d0e738d1c6f8c988145ad6d61df862f123bebd2ce0b9ff6d4
Tx public key: e01649a782fe62d3414d2261b8ceff1c90164d840505a75d073218eb2377a3cd
Timestamp: 1684949276 Timestamp [UCT]: 2023-05-24 17:27:56 Age [y:d:h:m:s]: 02:000:23:40:05
Block: 767220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522817 RingCT/type: yes/0
Extra: 01e01649a782fe62d3414d2261b8ceff1c90164d840505a75d073218eb2377a3cd02110000000133af99f4000000000000000000

1 output(s) for total of 1.761496683000 dcy

stealth address amount amount idx
00: 2b90741d29dc9f3e519499754320be0b8b09cba628ddc8bd2ef0dbb513316f15 1.761496683000 1216331 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": 767230, "vin": [ { "gen": { "height": 767220 } } ], "vout": [ { "amount": 1761496683, "target": { "key": "2b90741d29dc9f3e519499754320be0b8b09cba628ddc8bd2ef0dbb513316f15" } } ], "extra": [ 1, 224, 22, 73, 167, 130, 254, 98, 211, 65, 77, 34, 97, 184, 206, 255, 28, 144, 22, 77, 132, 5, 5, 167, 93, 7, 50, 24, 235, 35, 119, 163, 205, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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