Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e29f4d88a09fb384c247c158b49367c1cbed8c1112feecc14923d2255c71812

Tx prefix hash: 51e7677b7365118dd258bac06084a0424fedecf6899435ae9a84e91da0436bb6
Tx public key: 47c7b35e6c86c064e35de84f4c874ea5e4481aaeaaaccfe45cd9bbf0bd8a7472
Timestamp: 1710789596 Timestamp [UCT]: 2024-03-18 19:19:56 Age [y:d:h:m:s]: 01:029:01:12:48
Block: 981217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281729 RingCT/type: yes/0
Extra: 0147c7b35e6c86c064e35de84f4c874ea5e4481aaeaaaccfe45cd9bbf0bd8a747202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43119f023a28eafe0bf8a8a99d60973271e043f0378d890c5ca6f3554c5237c1 0.600000000000 1441310 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": 981227, "vin": [ { "gen": { "height": 981217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43119f023a28eafe0bf8a8a99d60973271e043f0378d890c5ca6f3554c5237c1" } } ], "extra": [ 1, 71, 199, 179, 94, 108, 134, 192, 100, 227, 93, 232, 79, 76, 135, 78, 165, 228, 72, 26, 174, 170, 172, 207, 228, 92, 217, 187, 240, 189, 138, 116, 114, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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