Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd0aa85a0b57fdb5583911509250752a84d0224b71f846d4bc7874b152591fe4

Tx prefix hash: 12b5d9029a0c2dea5e695a15b4a69d5fdd2b1b1694b2ca59ac7bb01876caf305
Tx public key: c1e038df5e2e774ec8044e838681772cd774f5e41f785afd369a274a4b13ad4a
Timestamp: 1725937657 Timestamp [UCT]: 2024-09-10 03:07:37 Age [y:d:h:m:s]: 00:189:15:53:16
Block: 1106783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135397 RingCT/type: yes/0
Extra: 01c1e038df5e2e774ec8044e838681772cd774f5e41f785afd369a274a4b13ad4a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a393e1172bb69ac73a4d25fb5adf0bf105b8f18024b0ef021b06d617065c27f 0.600000000000 1584384 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": 1106793, "vin": [ { "gen": { "height": 1106783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a393e1172bb69ac73a4d25fb5adf0bf105b8f18024b0ef021b06d617065c27f" } } ], "extra": [ 1, 193, 224, 56, 223, 94, 46, 119, 78, 200, 4, 78, 131, 134, 129, 119, 44, 215, 116, 245, 228, 31, 120, 90, 253, 54, 154, 39, 74, 75, 19, 173, 74, 2, 17, 0, 0, 0, 5, 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