Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb82a6a2796a67b4b4f156f1a60485fbd7b46e26cdd66caa7b3196c936056f6e

Tx prefix hash: 724a8f7aec3f03de1935660a089ea9bfe1123ba5e9c4e673e1881f6c61b8cb41
Tx public key: 65d6f9976120025c815271763468696d19fccc67ac8c2d3feb05a5836e900d16
Timestamp: 1720133240 Timestamp [UCT]: 2024-07-04 22:47:20 Age [y:d:h:m:s]: 00:314:23:12:11
Block: 1058653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225077 RingCT/type: yes/0
Extra: 0165d6f9976120025c815271763468696d19fccc67ac8c2d3feb05a5836e900d1602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d63fd8d2e13504b04142e7730ae68f29222ae152abe3d581ba262fde071f20b8 0.600000000000 1529110 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": 1058663, "vin": [ { "gen": { "height": 1058653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d63fd8d2e13504b04142e7730ae68f29222ae152abe3d581ba262fde071f20b8" } } ], "extra": [ 1, 101, 214, 249, 151, 97, 32, 2, 92, 129, 82, 113, 118, 52, 104, 105, 109, 25, 252, 204, 103, 172, 140, 45, 63, 235, 5, 165, 131, 110, 144, 13, 22, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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