Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6da1ae7a3ae147cba49105900f042b338f9f3aace9d07d7ee4e58d48d6e6d510

Tx prefix hash: 86d6da40753deb3a0a0795d6b827ac65e0af02c631eb9282e39a7142eff1d0c2
Tx public key: 7075c9789eb05001a210f7f1e76225e5a0927c2fcb4a47108d1afa5a1c029cbe
Timestamp: 1739301406 Timestamp [UCT]: 2025-02-11 19:16:46 Age [y:d:h:m:s]: 00:283:05:09:55
Block: 1217139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200168 RingCT/type: yes/0
Extra: 017075c9789eb05001a210f7f1e76225e5a0927c2fcb4a47108d1afa5a1c029cbe021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88aa74ef2abef9ab4288deddb0606677d1ce6520da97ea7107b2dac177d15c21 0.600000000000 1703948 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": 1217149, "vin": [ { "gen": { "height": 1217139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88aa74ef2abef9ab4288deddb0606677d1ce6520da97ea7107b2dac177d15c21" } } ], "extra": [ 1, 112, 117, 201, 120, 158, 176, 80, 1, 162, 16, 247, 241, 231, 98, 37, 229, 160, 146, 124, 47, 203, 74, 71, 16, 141, 26, 250, 90, 28, 2, 156, 190, 2, 17, 0, 0, 0, 2, 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