Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4a31d16ddfec67a3fdb7a1975f56ceef03b6fe31c35f6e6740000a066c4e2ab

Tx prefix hash: 81e093082d73331cdb78dc531f54af2389bd010da2b44d5dcab649fe26235ade
Tx public key: e8bbfbc3b862a0a2f63cef97bfdc39123acd01492344bcb38789d21d826b1d2e
Timestamp: 1682314307 Timestamp [UCT]: 2023-04-24 05:31:47 Age [y:d:h:m:s]: 01:223:02:29:06
Block: 745370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420915 RingCT/type: yes/0
Extra: 01e8bbfbc3b862a0a2f63cef97bfdc39123acd01492344bcb38789d21d826b1d2e021100000003e7ace25d000000000000000000

1 output(s) for total of 2.081037864000 dcy

stealth address amount amount idx
00: 959749cf3793b81c13a439b07fd3517740aa2793ae1f5dd34c5582abd4e36d4c 2.081037864000 1192813 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": 745380, "vin": [ { "gen": { "height": 745370 } } ], "vout": [ { "amount": 2081037864, "target": { "key": "959749cf3793b81c13a439b07fd3517740aa2793ae1f5dd34c5582abd4e36d4c" } } ], "extra": [ 1, 232, 187, 251, 195, 184, 98, 160, 162, 246, 60, 239, 151, 191, 220, 57, 18, 58, 205, 1, 73, 35, 68, 188, 179, 135, 137, 210, 29, 130, 107, 29, 46, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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