Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f632ad2db5b381e84c292176fb252ebe4180ad2f02047e64a228fd1175112a6

Tx prefix hash: a44d031c93b7f2e0090fc07c7d6172e65c80a3aaf3a56721cbbf857306b3889d
Tx public key: e5233e1069edecb1348157611f5c94ddc968921b0f5e6de4864c82a32c1039d0
Timestamp: 1713464875 Timestamp [UCT]: 2024-04-18 18:27:55 Age [y:d:h:m:s]: 01:221:01:41:27
Block: 1003362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416683 RingCT/type: yes/0
Extra: 01e5233e1069edecb1348157611f5c94ddc968921b0f5e6de4864c82a32c1039d002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35abfba290eaebed0012d081529c8bacf3d26a45b79587dfdc8f752ca2851caa 0.600000000000 1463892 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": 1003372, "vin": [ { "gen": { "height": 1003362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35abfba290eaebed0012d081529c8bacf3d26a45b79587dfdc8f752ca2851caa" } } ], "extra": [ 1, 229, 35, 62, 16, 105, 237, 236, 177, 52, 129, 87, 97, 31, 92, 148, 221, 201, 104, 146, 27, 15, 94, 109, 228, 134, 76, 130, 163, 44, 16, 57, 208, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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