Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec094a08c689b9d2e59c9c5174c35152f7919a2645d5f71a6555a3943fa2daeb

Tx prefix hash: 2d152fcaeb09c2ca075ac5f3f69ff1d21319ee5a82540754b3e0b99ba8ed466d
Tx public key: 96e8cba0a3f6f58e945710a81d6ff914f4cb2d127d40f7173f2395761bfba85f
Timestamp: 1624596394 Timestamp [UCT]: 2021-06-25 04:46:34 Age [y:d:h:m:s]: 03:322:00:27:17
Block: 283898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 997187 RingCT/type: yes/0
Extra: 0196e8cba0a3f6f58e945710a81d6ff914f4cb2d127d40f7173f2395761bfba85f02110000004ca9237c3a000000000000000000

1 output(s) for total of 70.364496718000 dcy

stealth address amount amount idx
00: 695368ad3d869118a31e439890aa6cb98e5f47ee3cc2d059fab07ff387eff21a 70.364496718000 594367 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": 283908, "vin": [ { "gen": { "height": 283898 } } ], "vout": [ { "amount": 70364496718, "target": { "key": "695368ad3d869118a31e439890aa6cb98e5f47ee3cc2d059fab07ff387eff21a" } } ], "extra": [ 1, 150, 232, 203, 160, 163, 246, 245, 142, 148, 87, 16, 168, 29, 111, 249, 20, 244, 203, 45, 18, 125, 64, 247, 23, 63, 35, 149, 118, 27, 251, 168, 95, 2, 17, 0, 0, 0, 76, 169, 35, 124, 58, 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