Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72da350d60b57f88e611667644e6e00078c79c05c91239e4f68aa23a1fa894a0

Tx prefix hash: 1cb067f52c4454a1435023d725fb2e94371dd5d31ff6916db9eb9beaa6ee2cd5
Tx public key: ff5bc7c634be5f5128cc770fb8cdd62b070b254ed1276bb0d99f318cbd9cbac3
Timestamp: 1711245819 Timestamp [UCT]: 2024-03-24 02:03:39 Age [y:d:h:m:s]: 01:073:18:45:58
Block: 985001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313723 RingCT/type: yes/0
Extra: 01ff5bc7c634be5f5128cc770fb8cdd62b070b254ed1276bb0d99f318cbd9cbac302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b612570e09e014946b64156f9b83c90a6c8e76375aba238b4c9ff015d0440d82 0.600000000000 1445206 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": 985011, "vin": [ { "gen": { "height": 985001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b612570e09e014946b64156f9b83c90a6c8e76375aba238b4c9ff015d0440d82" } } ], "extra": [ 1, 255, 91, 199, 198, 52, 190, 95, 81, 40, 204, 119, 15, 184, 205, 214, 43, 7, 11, 37, 78, 209, 39, 107, 176, 217, 159, 49, 140, 189, 156, 186, 195, 2, 17, 0, 0, 0, 1, 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