Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18f06b872d46b59e476d2741f95a4a1b1e38e41a38512d9ae937f16a3ee9185

Tx prefix hash: b59f7e27665f6addb45e0442dacfc9145f13b688da475e59a134178b3926aaab
Tx public key: 3e751b8cf128f97dec58c205cac3418452eedc0812b0cee7919b37e1bfeaa5c5
Timestamp: 1711451377 Timestamp [UCT]: 2024-03-26 11:09:37 Age [y:d:h:m:s]: 00:306:17:52:18
Block: 986709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219297 RingCT/type: yes/0
Extra: 013e751b8cf128f97dec58c205cac3418452eedc0812b0cee7919b37e1bfeaa5c502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 137f243e3e6a106d97d7f9ba29f6f74aa0bc602a79f7906d1600835c04706405 0.600000000000 1446942 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": 986719, "vin": [ { "gen": { "height": 986709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "137f243e3e6a106d97d7f9ba29f6f74aa0bc602a79f7906d1600835c04706405" } } ], "extra": [ 1, 62, 117, 27, 140, 241, 40, 249, 125, 236, 88, 194, 5, 202, 195, 65, 132, 82, 238, 220, 8, 18, 176, 206, 231, 145, 155, 55, 225, 191, 234, 165, 197, 2, 17, 0, 0, 0, 5, 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