Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b20bf6bbed6bc35118ab32a35abfe1cfb1c1e2f615231de475be89e87ce2841

Tx prefix hash: 199f63ac833847e1651592283dcf8364246a162bccefef29747c445d69b9d599
Tx public key: bd1df36ecfe912426d9c7bbd2f92df235c2a7cdc187e336fabb45e13bde99d1a
Timestamp: 1689006696 Timestamp [UCT]: 2023-07-10 16:31:36 Age [y:d:h:m:s]: 01:231:23:23:54
Block: 800869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426884 RingCT/type: yes/0
Extra: 01bd1df36ecfe912426d9c7bbd2f92df235c2a7cdc187e336fabb45e13bde99d1a02110000000633af99f4000000000000000000

1 output(s) for total of 1.362663663000 dcy

stealth address amount amount idx
00: a7c2c1493c4eefdf55a3213b71fc0fd6713dd7bf97deed762593d99ea6f7873d 1.362663663000 1251938 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": 800879, "vin": [ { "gen": { "height": 800869 } } ], "vout": [ { "amount": 1362663663, "target": { "key": "a7c2c1493c4eefdf55a3213b71fc0fd6713dd7bf97deed762593d99ea6f7873d" } } ], "extra": [ 1, 189, 29, 243, 110, 207, 233, 18, 66, 109, 156, 123, 189, 47, 146, 223, 35, 92, 42, 124, 220, 24, 126, 51, 111, 171, 180, 94, 19, 189, 233, 157, 26, 2, 17, 0, 0, 0, 6, 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