Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cc79a6b8391bf7bd894593fe4ac78829d4826dac21f455c8354d835547e8678

Tx prefix hash: d96a3cc3a4dafa5b84708c93c24521cb9690f6973912f96d823761fa91269b25
Tx public key: af3f8a113a71425d38d6e4017a3a1c5cc4d5bfd3409c772118efb2d80072360a
Timestamp: 1722301917 Timestamp [UCT]: 2024-07-30 01:11:57 Age [y:d:h:m:s]: 00:246:22:32:58
Block: 1076636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176381 RingCT/type: yes/0
Extra: 01af3f8a113a71425d38d6e4017a3a1c5cc4d5bfd3409c772118efb2d80072360a021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97e0bfde13f19b6c5ae6fc096e2f1ec44c03e73482418555abd1240ed863c7c9 0.600000000000 1549177 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": 1076646, "vin": [ { "gen": { "height": 1076636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97e0bfde13f19b6c5ae6fc096e2f1ec44c03e73482418555abd1240ed863c7c9" } } ], "extra": [ 1, 175, 63, 138, 17, 58, 113, 66, 93, 56, 214, 228, 1, 122, 58, 28, 92, 196, 213, 191, 211, 64, 156, 119, 33, 24, 239, 178, 216, 0, 114, 54, 10, 2, 17, 0, 0, 0, 9, 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