Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7abb0c1d6d3ccaa15038ba015ed5cb1ea12511bf94cf2a83f5f2b1c32525b87

Tx prefix hash: 58d11b57a26c69b117b50b111403b640175559c79905f9f7b3a481a0b1579d25
Tx public key: da90ce3cbac793528eb16c8595848ef004a931a1c063af006959c76b96f803d3
Timestamp: 1736900608 Timestamp [UCT]: 2025-01-15 00:23:28 Age [y:d:h:m:s]: 00:309:07:38:01
Block: 1197520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218587 RingCT/type: yes/0
Extra: 01da90ce3cbac793528eb16c8595848ef004a931a1c063af006959c76b96f803d3021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7ce91bba1dbdc0a4f4ce8fb91d2cac93440accb40df506c58d865f9c2eb67e1 0.600000000000 1684129 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": 1197530, "vin": [ { "gen": { "height": 1197520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7ce91bba1dbdc0a4f4ce8fb91d2cac93440accb40df506c58d865f9c2eb67e1" } } ], "extra": [ 1, 218, 144, 206, 60, 186, 199, 147, 82, 142, 177, 108, 133, 149, 132, 142, 240, 4, 169, 49, 161, 192, 99, 175, 0, 105, 89, 199, 107, 150, 248, 3, 211, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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