Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e51b6313256ed2696cef491282d10d970c2ea9b8b0b06aa99eff4cf645e7d430

Tx prefix hash: a58a0639bad2fd92764d361a9ebc74131b40ecb625b8ae47a170d0f4948fd5fa
Tx public key: c633037923e99d967e179e5a8885deb0984159c27d6a73857a4931ca8bf6b908
Timestamp: 1658962179 Timestamp [UCT]: 2022-07-27 22:49:39 Age [y:d:h:m:s]: 02:111:13:41:26
Block: 553141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601099 RingCT/type: yes/0
Extra: 01c633037923e99d967e179e5a8885deb0984159c27d6a73857a4931ca8bf6b90802110000001265468698000000000000000000

1 output(s) for total of 9.020162778000 dcy

stealth address amount amount idx
00: 1973a5a92ab8cbea84cb0fac0e0379a13ff0b3f9a83d7e51d3d0f76be88c6ae0 9.020162778000 984913 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": 553151, "vin": [ { "gen": { "height": 553141 } } ], "vout": [ { "amount": 9020162778, "target": { "key": "1973a5a92ab8cbea84cb0fac0e0379a13ff0b3f9a83d7e51d3d0f76be88c6ae0" } } ], "extra": [ 1, 198, 51, 3, 121, 35, 233, 157, 150, 126, 23, 158, 90, 136, 133, 222, 176, 152, 65, 89, 194, 125, 106, 115, 133, 122, 73, 49, 202, 139, 246, 185, 8, 2, 17, 0, 0, 0, 18, 101, 70, 134, 152, 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