Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63aa1c3304b41e40cf6ea1639b368fb1522b64cecf5b237820d6aab18064c01

Tx prefix hash: c0d10e3fb203ef1744421e3ef1fafa31e4603e0a090748c2aa885d8114ee1dbe
Tx public key: 2a8b3793f45eb7f49d35d38f8ccfcec2e64e5624d0e8308874e075da0afe9e7a
Timestamp: 1683488083 Timestamp [UCT]: 2023-05-07 19:34:43 Age [y:d:h:m:s]: 01:249:17:25:42
Block: 755102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439934 RingCT/type: yes/0
Extra: 012a8b3793f45eb7f49d35d38f8ccfcec2e64e5624d0e8308874e075da0afe9e7a02110000000133af99f4000000000000000000

1 output(s) for total of 1.932118736000 dcy

stealth address amount amount idx
00: f9e943222b051fa5c6d05714f3916e0a5fd4fd8bbbb880391c0901b517a00afb 1.932118736000 1203401 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": 755112, "vin": [ { "gen": { "height": 755102 } } ], "vout": [ { "amount": 1932118736, "target": { "key": "f9e943222b051fa5c6d05714f3916e0a5fd4fd8bbbb880391c0901b517a00afb" } } ], "extra": [ 1, 42, 139, 55, 147, 244, 94, 183, 244, 157, 53, 211, 143, 140, 207, 206, 194, 230, 78, 86, 36, 208, 232, 48, 136, 116, 224, 117, 218, 10, 254, 158, 122, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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