Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb3af853152c2fd16ebbb3f4c1346368e30a0875a28c3f4fe0cff7b4eb86b1a

Tx prefix hash: 4be115aea89d760ac43e9965ecbdf959542b3e6d1a28f3250ad8ff0da1598935
Tx public key: 71659a399e2cb8f62bf938f86f9906f788f9524bd3dce4db4844c66faaa49990
Timestamp: 1646622336 Timestamp [UCT]: 2022-03-07 03:05:36 Age [y:d:h:m:s]: 03:239:10:14:42
Block: 452985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 948969 RingCT/type: yes/0
Extra: 0171659a399e2cb8f62bf938f86f9906f788f9524bd3dce4db4844c66faaa49990021100000008c9067537000000000000000000

1 output(s) for total of 19.367471537000 dcy

stealth address amount amount idx
00: 4e31be9c4c60bc516c50f7ba655f50547377ab5c451c8754e028f7360f8e5b2a 19.367471537000 868384 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": 452995, "vin": [ { "gen": { "height": 452985 } } ], "vout": [ { "amount": 19367471537, "target": { "key": "4e31be9c4c60bc516c50f7ba655f50547377ab5c451c8754e028f7360f8e5b2a" } } ], "extra": [ 1, 113, 101, 154, 57, 158, 44, 184, 246, 43, 249, 56, 248, 111, 153, 6, 247, 136, 249, 82, 75, 211, 220, 228, 219, 72, 68, 198, 111, 170, 164, 153, 144, 2, 17, 0, 0, 0, 8, 201, 6, 117, 55, 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