Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c633d02223a79fea724164f241653ebf0d302ceaa39d06c3dc62c789fa84672

Tx prefix hash: bba23f9d745b905fbff54c3ea434a9e4c1acb9f9cce7e1a4d012984f94df3683
Tx public key: 0a4e84a4180cda976cf42821c4bb92478b8adb5955861873f1c5f1c84c05a88b
Timestamp: 1582423416 Timestamp [UCT]: 2020-02-23 02:03:36 Age [y:d:h:m:s]: 04:309:06:25:41
Block: 70478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113692 RingCT/type: yes/0
Extra: 010a4e84a4180cda976cf42821c4bb92478b8adb5955861873f1c5f1c84c05a88b0211000000238a2ee0d9000000000000000000

1 output(s) for total of 358.490731804000 dcy

stealth address amount amount idx
00: ead81e4a07b9cf1d7bbcf1a819a78976288edfbb4db0a72febb3e797e5f9e449 358.490731804000 130254 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": 70488, "vin": [ { "gen": { "height": 70478 } } ], "vout": [ { "amount": 358490731804, "target": { "key": "ead81e4a07b9cf1d7bbcf1a819a78976288edfbb4db0a72febb3e797e5f9e449" } } ], "extra": [ 1, 10, 78, 132, 164, 24, 12, 218, 151, 108, 244, 40, 33, 196, 187, 146, 71, 139, 138, 219, 89, 85, 134, 24, 115, 241, 197, 241, 200, 76, 5, 168, 139, 2, 17, 0, 0, 0, 35, 138, 46, 224, 217, 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