Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351eb61b86e7a8173d2b7053fdb900e4a0fe74ea03af9f82cce7c529ad6e891f

Tx prefix hash: 72feab585539fb82632fda83c52c6e53488a5c1e3b6e410577a8bbe81541d7b7
Tx public key: f3b48b56410a2cc2820694178189268aab05f0e3199a8d27ac72a7558ec954a3
Timestamp: 1722926741 Timestamp [UCT]: 2024-08-06 06:45:41 Age [y:d:h:m:s]: 01:092:19:27:48
Block: 1081812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324806 RingCT/type: yes/0
Extra: 01f3b48b56410a2cc2820694178189268aab05f0e3199a8d27ac72a7558ec954a3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9014f0cdd0c68047f2617cef260fc1c7e2e7abbb1ef5c40fde4922d42c549679 0.600000000000 1555635 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": 1081822, "vin": [ { "gen": { "height": 1081812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9014f0cdd0c68047f2617cef260fc1c7e2e7abbb1ef5c40fde4922d42c549679" } } ], "extra": [ 1, 243, 180, 139, 86, 65, 10, 44, 194, 130, 6, 148, 23, 129, 137, 38, 138, 171, 5, 240, 227, 25, 154, 141, 39, 172, 114, 167, 85, 142, 201, 84, 163, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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