Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6200607fc856eba244a2b1556631583aaba17f3eb50078c07470ca67ceb97bc2

Tx prefix hash: 73e93a602c8dd133118084f643f5dbdf83347a9426ba7e19a040aae876c5c4b3
Tx public key: cd0e07d6949b6e2315b9bb52ccb789f1ee3d094d40394db65fca89a5bacbf817
Timestamp: 1730834084 Timestamp [UCT]: 2024-11-05 19:14:44 Age [y:d:h:m:s]: 00:070:11:14:04
Block: 1147286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50421 RingCT/type: yes/0
Extra: 01cd0e07d6949b6e2315b9bb52ccb789f1ee3d094d40394db65fca89a5bacbf817021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b75653b121b0125bea8d6bb7495b0cb49f4fd349dc807afc8f76f5c6e31d4c4 0.600000000000 1631981 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": 1147296, "vin": [ { "gen": { "height": 1147286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b75653b121b0125bea8d6bb7495b0cb49f4fd349dc807afc8f76f5c6e31d4c4" } } ], "extra": [ 1, 205, 14, 7, 214, 148, 155, 110, 35, 21, 185, 187, 82, 204, 183, 137, 241, 238, 61, 9, 77, 64, 57, 77, 182, 95, 202, 137, 165, 186, 203, 248, 23, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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