Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656a02b2e3d2990b534fa72c532d9f5ba17ab0f304156ab61e7a3ae4a5ef58c0

Tx prefix hash: 24a70e6b3d719575cb67453b3e3133085497087b6b1e883f1c64b70c4cdfedec
Tx public key: 53b3f3fadd214c9fe651f62af1d8d24c4a2f13f78336691436a4f15822bc0a81
Timestamp: 1577112948 Timestamp [UCT]: 2019-12-23 14:55:48 Age [y:d:h:m:s]: 05:015:12:02:58
Block: 30001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161169 RingCT/type: yes/0
Extra: 0153b3f3fadd214c9fe651f62af1d8d24c4a2f13f78336691436a4f15822bc0a81021100000001d81c26c0000000000000000000

1 output(s) for total of 488.196987581000 dcy

stealth address amount amount idx
00: 3d2ca0ff2d4577ae831712a876d34a0d313f3aa6b4f801f1916ffc1f2e063f67 488.196987581000 49523 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": 30011, "vin": [ { "gen": { "height": 30001 } } ], "vout": [ { "amount": 488196987581, "target": { "key": "3d2ca0ff2d4577ae831712a876d34a0d313f3aa6b4f801f1916ffc1f2e063f67" } } ], "extra": [ 1, 83, 179, 243, 250, 221, 33, 76, 159, 230, 81, 246, 42, 241, 216, 210, 76, 74, 47, 19, 247, 131, 54, 105, 20, 54, 164, 241, 88, 34, 188, 10, 129, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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