Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29442a50ad61641bdabae9583c603bcc6ba928fa322c5fcee7bf33cded1818b5

Tx prefix hash: cc1c82ba39b41ca97c7bb17ae80397e3a90193b1f57fc947021be07811898536
Tx public key: f6a43b7e44be6c052cbdcb9f2e5df9c2a55985535637f56d29d98f8a49844f0e
Timestamp: 1733532493 Timestamp [UCT]: 2024-12-07 00:48:13 Age [y:d:h:m:s]: 00:105:11:04:01
Block: 1169643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75171 RingCT/type: yes/0
Extra: 01f6a43b7e44be6c052cbdcb9f2e5df9c2a55985535637f56d29d98f8a49844f0e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acb2c634c068d06c5836edccd17870be593e62d5912882af703fe6f486eb658e 0.600000000000 1655366 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": 1169653, "vin": [ { "gen": { "height": 1169643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acb2c634c068d06c5836edccd17870be593e62d5912882af703fe6f486eb658e" } } ], "extra": [ 1, 246, 164, 59, 126, 68, 190, 108, 5, 44, 189, 203, 159, 46, 93, 249, 194, 165, 89, 133, 83, 86, 55, 245, 109, 41, 217, 143, 138, 73, 132, 79, 14, 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