Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8c8c416b3b53d9892cfb24b8b41d5ab129638d18581c20514053b615645da97

Tx prefix hash: 777a2e79d440c9ed1d2b9671669ad990fe2108aaf32a7ca135ed511ab332dd9b
Tx public key: 23f70eb425db68a97529ab710dc5aa382d712aee4b45bb70785b3c9151463a75
Timestamp: 1574542519 Timestamp [UCT]: 2019-11-23 20:55:19 Age [y:d:h:m:s]: 05:078:06:59:16
Block: 15903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1198631 RingCT/type: yes/0
Extra: 0123f70eb425db68a97529ab710dc5aa382d712aee4b45bb70785b3c9151463a75021100000009f95225a5000000000000000000

1 output(s) for total of 543.635291313000 dcy

stealth address amount amount idx
00: 961f63cb55b5096a20baab3125d31a114fdfcdc5da19c8cfbd45fbcf7b4fa0ec 543.635291313000 21727 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": 15913, "vin": [ { "gen": { "height": 15903 } } ], "vout": [ { "amount": 543635291313, "target": { "key": "961f63cb55b5096a20baab3125d31a114fdfcdc5da19c8cfbd45fbcf7b4fa0ec" } } ], "extra": [ 1, 35, 247, 14, 180, 37, 219, 104, 169, 117, 41, 171, 113, 13, 197, 170, 56, 45, 113, 42, 238, 75, 69, 187, 112, 120, 91, 60, 145, 81, 70, 58, 117, 2, 17, 0, 0, 0, 9, 249, 82, 37, 165, 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