Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f47e37e1933be38083c5c108873f75cc935f5ec8e6d0f37d9f6522d2175e8eff

Tx prefix hash: 888c683156fda2df4fd4b0901a687bb49bc82b4eba2685bed77fea4ef96592ee
Tx public key: c211a00a90ec211e9158a6fb7a421584f78e994c4c858a9fba9f1462079cc904
Timestamp: 1721328625 Timestamp [UCT]: 2024-07-18 18:50:25 Age [y:d:h:m:s]: 00:285:13:42:03
Block: 1068585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204036 RingCT/type: yes/0
Extra: 01c211a00a90ec211e9158a6fb7a421584f78e994c4c858a9fba9f1462079cc90402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76a6f3d145caf2a74dcabe74fe01ea8ccea97033cff5829f954fbbc15cdf123c 0.600000000000 1539666 of 15

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": 1068595, "vin": [ { "gen": { "height": 1068585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76a6f3d145caf2a74dcabe74fe01ea8ccea97033cff5829f954fbbc15cdf123c" } } ], "extra": [ 1, 194, 17, 160, 10, 144, 236, 33, 30, 145, 88, 166, 251, 122, 66, 21, 132, 247, 142, 153, 76, 76, 133, 138, 159, 186, 159, 20, 98, 7, 156, 201, 4, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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