Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b07700d929bce76992f752fb4e2758363655271e39e45a4496731932691f34

Tx prefix hash: c5dcab0327283200c5070ecdb5777f9cbd69aa5575ac8731673a9fb1f1bf9bee
Tx public key: bc75e0a22e9a6029e43e6a1b3854f3a83472926155354e0062b4272395811bee
Timestamp: 1722977177 Timestamp [UCT]: 2024-08-06 20:46:17 Age [y:d:h:m:s]: 00:200:15:46:32
Block: 1082229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143269 RingCT/type: yes/0
Extra: 01bc75e0a22e9a6029e43e6a1b3854f3a83472926155354e0062b4272395811bee021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9f0c932a90068a97b233e09b8f2cf58499e7edb28c005b34a7c8c67fd1362ce 0.600000000000 1556054 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": 1082239, "vin": [ { "gen": { "height": 1082229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9f0c932a90068a97b233e09b8f2cf58499e7edb28c005b34a7c8c67fd1362ce" } } ], "extra": [ 1, 188, 117, 224, 162, 46, 154, 96, 41, 228, 62, 106, 27, 56, 84, 243, 168, 52, 114, 146, 97, 85, 53, 78, 0, 98, 180, 39, 35, 149, 129, 27, 238, 2, 17, 0, 0, 0, 4, 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