Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85250bc1a0e4c92d020bce26b061f1394e658c5c735e9b160545a791e7c62cdc

Tx prefix hash: 7173088a6785206666499778daa0fb1152fabd5716a5059501c742e9700a3e0c
Tx public key: 033abbe6cda1f9e34bcd7f289d6d611be75bb2a1e70c4fa11d62680daea9369b
Timestamp: 1643291340 Timestamp [UCT]: 2022-01-27 13:49:00 Age [y:d:h:m:s]: 02:306:08:21:47
Block: 426381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737454 RingCT/type: yes/0
Extra: 01033abbe6cda1f9e34bcd7f289d6d611be75bb2a1e70c4fa11d62680daea9369b02110000000206faf294000000000000000000

1 output(s) for total of 23.725919973000 dcy

stealth address amount amount idx
00: 28dd99732897d58b1f57b6f009229e3ed7f07cce4ac4408dd05e4966824cbfb2 23.725919973000 835198 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": 426391, "vin": [ { "gen": { "height": 426381 } } ], "vout": [ { "amount": 23725919973, "target": { "key": "28dd99732897d58b1f57b6f009229e3ed7f07cce4ac4408dd05e4966824cbfb2" } } ], "extra": [ 1, 3, 58, 187, 230, 205, 161, 249, 227, 75, 205, 127, 40, 157, 109, 97, 27, 231, 91, 178, 161, 231, 12, 79, 161, 29, 98, 104, 13, 174, 169, 54, 155, 2, 17, 0, 0, 0, 2, 6, 250, 242, 148, 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