Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2ae8017c4fb50398387ee5ecc157b0d0793bb28b71808971b3af9a823208db

Tx prefix hash: 36f88e0ba827556904fff8ae0134ebe5469d0c757fa471c606701161d2bd0094
Tx public key: fba26e306dd6c75f0f2bb872ed7d26e7a065b0f0f6e1b520c362c2e5a922a2f4
Timestamp: 1723356713 Timestamp [UCT]: 2024-08-11 06:11:53 Age [y:d:h:m:s]: 00:233:20:55:52
Block: 1085378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167021 RingCT/type: yes/0
Extra: 01fba26e306dd6c75f0f2bb872ed7d26e7a065b0f0f6e1b520c362c2e5a922a2f4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: facb5b9711d24dffdc41bd5157aa36349d0b17a84b89a514e8ed48fbf43025a6 0.600000000000 1559951 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": 1085388, "vin": [ { "gen": { "height": 1085378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "facb5b9711d24dffdc41bd5157aa36349d0b17a84b89a514e8ed48fbf43025a6" } } ], "extra": [ 1, 251, 162, 110, 48, 109, 214, 199, 95, 15, 43, 184, 114, 237, 125, 38, 231, 160, 101, 176, 240, 246, 225, 181, 32, 195, 98, 194, 229, 169, 34, 162, 244, 2, 17, 0, 0, 0, 1, 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