Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ed7ce8ac8f49306b33206f16e9f1c22a8a511556c1ca896b4cba0cdc70827d1

Tx prefix hash: 1ff9272f58e4ad4b06d5c8d18aab5b430744721301472249a7316525f3d88be7
Tx public key: 39cae9c25b17ff9e58a4fda690655b86630a7bdd0d02c658d21b70d725e00fe1
Timestamp: 1710645399 Timestamp [UCT]: 2024-03-17 03:16:39 Age [y:d:h:m:s]: 01:235:22:54:53
Block: 980021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427317 RingCT/type: yes/0
Extra: 0139cae9c25b17ff9e58a4fda690655b86630a7bdd0d02c658d21b70d725e00fe102110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eafe5d26b3595a627d697ae39916278afd2f227042359074e8458f5bd7a42a7f 0.600000000000 1440080 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": 980031, "vin": [ { "gen": { "height": 980021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eafe5d26b3595a627d697ae39916278afd2f227042359074e8458f5bd7a42a7f" } } ], "extra": [ 1, 57, 202, 233, 194, 91, 23, 255, 158, 88, 164, 253, 166, 144, 101, 91, 134, 99, 10, 123, 221, 13, 2, 198, 88, 210, 27, 112, 215, 37, 224, 15, 225, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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